Hello, |
Re: DOORS database backup In answer to each of your questions. 1. It's just not practical to try and back-up specific module\project data from the DOORS database area. You can only do module\project level back-ups using the Archive & Restore features which are part of the DOORS client. Use the Help menu to read up about these two features. You will need to write a DXL batch script that will Archive the Projects and modules that need to be specifically backed up - this batch script will then need to be scheduled to run overnight, but make sure that it doesn't clash with the full data back-up. 2. As far as I know there are no DOORS manuals that explain the structure of the DOORS database area. Unless you have grown up with this tool and seen how the database area has changed over time, it's just too complicated to try and explain in this forum unless someone else would like to give it a go. 3. Do a full overnight back-up every day. Make sure that the database service is stopped prior to starting each back-up and is restarted after each back-up is completed. Users need to be made aware that they need to log-off at the end of each day so that the overnight back-up is clean and there are no data locks in place. As for restoring - I always have a development level DOORS database area that I use for testing and can also be used to dump a full back-up so that I can check that the restore works. If it all looks OK, then the full back-up can be restored into the production level DOORS database area. Depending on the depth of your DOORS experience, it may not be necessary to do a full restore in the production area - just restore into the development area and use the DOORS Archive and Restore features to selectively replace whole Projects or individual Modules. However, this approach requires immense care and solid User and Administration level experience with DOORS. Paul Miller |